fort monroe

C2PC Measures of Effectiveness

(MOE)

\/circinn 9 f)

Jjy

NAI Alert

t_l±

DP Alert

*UJ]

®u| dr •=;“ 0°

'jBBI

1 II.MH 3 I

iuc -nPH pJ 4i p ■ -ri km

CO .41 }iAJ 1

J

| - _J CZPC N et™fc 5 Wui

Hiv^ih Coile \lert!

IFT"MXP

|u hi

H 1 TFTPJ ■

4 11 WAF

4- ihwv=

4- IttWWW

JL "ra.ILLIY C

4 5MAF

4 f .il t' im .m\

m j Vlrrt!

i|M|i.H

JV«r<

■ -UMFli

El

IOI) \lrli!

BPr*~M4F

k-- WPn«M'

i n A > «-

r Di4>fic4te Tucks

# TF33

4 LiBh

- _J MDE bd |

U uc.k AJtT&J* Eh*
W _J “ rtdflip ?PlD
0 j 'nwJ*(»*HD5
W J MissngFFO
E! _J Mi5±tpj Wlli
_i IXcfede Tr-acfc ?

I Adlvft Wf IF Ajfefli

p f? wy/TAa
V Piston F orl
p [? UK?<WD

13 & 9iEMtyCDfle
p h : T 1K*.3

S Miis±->j Kejj T ixhs

r * , /d7

r:prw*t m t r ,hjrfn:

... i

krT I tuiU \lt-rt I

■ ppll V l|v '"ZT*' Tipi Jfc i

MTO \lrrt!

ra 4 r

rl ■ r Hi

Kef I rark Aim!

■ i p pi" - i p ■! "-d m Hb" i "iP

V\| AI«-tT

mua

hue Mi '■ wip-J -Vi ■ ■ i+ litpiffr

nui >-ai i

]

The Titan Corporation, Tactical
Services Division
(757) 671-2554
cb.brown@titan.com

Objective

• Develop an injector that provides the Commander an
“actionable" sitmap in C2PC by monitoring and alerting
on key events during the execution of his battle plan.

- Focus on improved unit reporting via the C4I architecture.

- Focus on increased use of C2PC

- Focus on maintaining the CTP

- Focus on the timeliness of the CTP

- Focus on the accuracy of the CTP

- Focus on the completeness of the CTP

Increase the Commander's confidence in the C2PC CTP.

The MOE Task

• Measure of Effectiveness (MOE) injector for C2PC.

• Monitoring Agents/Knowledge Management rule
sets for monitoring the execution of the battle
plan using C2PC application.

• Make C2PC more useful for MAGTF Commanders
and his battlestaffs/action officers!

• Active CTP graphics alert for critical events and
decision points across the battlefield.

• Maximize C2PC API and current injector features

Commander's tool for monitoring the
battlespace will inherently increase the use of
C2PC

C2PC MOE Feature Set

• NAI/DP/LD Alerts

• Track Attribute Agent

• Duplicate Track Agent

• Missing Tracks Agent

• Brevity Code Agent

• Key Track Agent

• Movement to Objective

• C2PC Network Status

• Alert Logs

C2PC MOE Development

vi

- Currently on IOW 3.6

- Stand alone application outside C2PC

- Access via C2PC Measures of Effectiveness menu in
C2PC Menu Group

- Designed for C2PC 5.8.2 but works with C2PC 5. 9. 0.3

V2

- Projected for IOW 3.6.5

- Fully embedded C2PC Injector

- Greatly enhanced

- Designed for C2PC 5. 9. 0.3

C2PC MOE VI Application

Abstract Requirements/Capabilities

- Develop a simple User Interface for
allowing the Watch Officer/Chief to
select when and which "rules" to
activate.

- Passively monitor the C2PC
databases for the critical events to
happen and report those events as
they occur.

- Allow independent views and rules
for each action officer.

- Look at what is "NOT" there as well
as what is there.

- Monitor your CTP network.

- Develop "active" graphical objects to
monitor the battlespace for events.

Measures of Effectiveness

File Options Graphics View Logs Help

-IqJjsJ

TimeLate/Attribute/Missing List

Track Narine

<1

Select All

Clear All

List Selection
f* Attribute
C TimeLate FRD
TimeLate HOS
C Missing FRD
C Missing HOS

Alert Selection

r Message

Dec Point
QNAI/TAI
I - Brevity Code
V~ Key T rack
V~ KT Missing
r |MT0|

r LOD/Bnd

Send Email

Addresses

MOE Criteria

NAI/TAI Agent

NAI/TAI - Named
Areas of
Interest/Target
Area of Interest -
is a simple utility
that the S-2 can
use to monitor a
NAI/TAI for enemy
activity.

You can choose
the desired color
and shape (circle
or box) for the
NAI/TAI. MOE
monitors for any
HOS/SUS unit
breaching or
leaving the
geometry of the
NAI/TAI.

NAI/TAI uses pop-
up dialogs and, if
desired, sound to
alert events.

C2PC MOE V2 Injector

Requirements/Capabilities

- Develop a simple User Interface for
allowing the Watch Officer/Chief to
select when and which "rules" to
activate.

- Passively monitor the C2PC databases
for the critical events to happen and
report those events as they occur.

- Allow independent views and rules for
each action officer.

- Assess what is "NOT" there as well as
what is there.

- Evaluate beyond "operator's current
map view"

- Monitor CTP reporting network.

- Develop "active" graphical objects to
monitor the battlespace for events.

- Implement easy methods for enabling
and disabling alert pop-ups.

©u

*r| ©0

M

B a MOE List

s-O T rack Attribute Check

h-]-CU Timelate FRD
lil-Hn Timelate HOS
| |-Q Missing FRD

S-CJ Missing HOS
EH--CJ Duplicate Tracks
E Active MOE Alerts
I El-0 NAI/TAI
+]•• ✓ Decision Point
| i-0 LOD/BND
+]•• Brevity Code
EI-0 Key Tracks
El-0 Missing Key Tracks
s □ MW

E _A C2PC Network Status

| ^ 11 MAR

| ^ 1MAR

I 'h 2BN5MAR

I ^ 5MAR

| ^ 7MAR

i 'h I MEF

Action Officers can
specify Timelate and
attribute reporting
criteria.

MOE "watches" the
database and reports
which FRIENDLY and
HOSTILE unit tracks
reports are too old
and which friendly
units are not
reporting the desired
data.

When updated, the
tracks will
automatically be
removed from the
list.

Ideally, these lists
would be empty
which means all the
tracks are reporting
the right data and
are up to date.

TimeLate and Attribute

Aaent

§ C2PC - WGS 1984: Global Definition - [moe.map - CAMP_PENDLETON - 1:50K]

H File MOE View Map Favorites Declutter Tools Window Help

■a ® • o

S' ’ SIS ?

m These tracks are NOT

'v:;7r

§1 reporting their combat
1 effectiveness

M These friendly tracks are
P more than 10 minutes

ieLate Reporting Period (minutes)

Friendly

Hostile

These hostile tracks are
more than 20 minutes
old.

Select All

Clear All

000:01 : 1 15MS58587891 10

. WFNS5MAR

&ks 9

PU. w;- MH.rh

Track Attributes

115M55855 139074

0l| £ 2t|»f|©c^^

□ u MOE List

EF-ij Track Attribute Check

♦

♦

♦

♦

♦

♦

1BN7MAR
3BN7MAR
TF BRAVO
1LARBN
MAG 39
TF33

Pij Timelate FRD
+ 1BN7MAR
+ TF BRAVO
+ TF22

♦ 1BN5MAR
+ 1LARBN
+ TF33

S-Q Timelate H0S
+ UIBN

♦ 311MRB

♦ 31MRR
$ _J Missing FRD
+ _] Missing H0S
El ■■■□ Duplicate Tracks

Fh-I I Active MOE Alerts
■ f'l C2PC Network Status

F| ag

|— Equipment
Type

I - Course

Higher

Formation

j|plf Speed

|” Eval Rating

r u| c

rj Combat
Effectiveness

i^|5tart| |j ^\\192.168.1.100\share | PdCiiProoram Files

C2PC - WGS 1984: ...

lMOE InstallShield Test, . , E] Track Attributes

5:01 PM

G u...

•r.|

Qo...

^£m..|

B -\!/ |

-r

1MARDIV
^ I\l

r 25RAG

Q-r 31MRR

r 311MRB
r 312MRB
-IHT 5MAR

r 2BN5MAR
r WPN5 CO 5MAR
MAG 39

H r & Targets

Units Injector - Planned
MAGTF Organization

The current CTP is
continuously
checked against the
pre-planned
"Units" database
for the MAGTF
organization and
Threat OOB.

Missing iracks
Agent

I«M

®o |

M..|

MOE List

1+ | T rack Attribute Check

Iti-fli Timelate FRD
IS [p Timelate HOS
R -Pil Missing FRD

RUAR

I

1MARDIV

ZETTOMmIi

E; Q Missing HOS
+ 312MRB
♦ 25RAG

■ I n ■ 1 1—. 1 1 . V T r - . 1 .■

Missing Track
agent identifies
FRIENDLY and
Hostile tracks that
are NOT in the
current track
database.

c : \program f iles\usmc\data\local\c2|

[+ | Platforms

E- _J Units

1BN5MAR
1BN7MAR
1LARBN
311MRB
31MRR

^ 3BN7MAR
MAG 39
TF BRAVO
TF22
TF33
TF33]

UI BN

WPN55MAR

TrackPlot Injector -
shows units currently
in the CTP

Duplicate Tracks Agent

EH_d c:\ptogram filts\uHnc\data\

1=1 ' 'j Platforms

. n UL acft
ra US5 WASP I

:jtee

1BN1MAR
1BN5MAR
1MAR
IMAP
2BN1MAR
3BN5MAR

am

UI Ad
UIBN
UIBN.

U] RGT
U5S WASP

C*l h

Hrjj MOE List

I Track Attribute Check
J1 CJ TimdaleFRD
*] Timolato HOS
$ _J Mitsing F1HD
if _J Missing HOS
- Duplicate Tracks
E T rackname
+ 1 MAR
+ UI ACFT

♦ UI BN
+ US 5 WASP
UIC

♦ INF 5 M. 1 BNfilvtAB

♦ INF 5 M. 3 BNSMAR

* j Active MOE Alnts

_| C2RC Network Sttfuj

E-Q MOE List

! : □ T rack Attribute Check

+ n Timelate FRD
+ -CJ Timelate HOS
| 3_l Missing FRD

+ L_3 Missing HOS
- _J Duplicate Tracks
FI Q T rackname
- _J UIC

j + INF5MJBN5MAR

i ♦ INF5M, 3BN5MAFI

i+>- n 1 Active MOE Alerts
| C2PC Network Status

OTH REAL-WORLD LU00898 lOTH REAL-WORLD LU00899

Attributes j Symbology j T rack N Attributes j Symbology j T rack

Name:

|1BN5MAR

Short Name:

|1BN5MAR

Alert:

NONE

Category:

LND

Threat:

FRD

Flag:

T

Real World
/ Exercise:
UIC:

REAL-WORLD

|INF5M

Name:

|3BN5MAR

Short Name:

|3BN5MAR

Alert:

NONE

Category:

LND

Threat:

FRD

Flag:

T

Real World
/ Exercise:
UIC:

REAL-WORLD

|INF5M

Duplicate Tracks Agent monitors
the unit track database and lists
units that have the same track
name (long name), Unit
Identification Code (UIC) and/or
the same Unit Reference Number
(URN). In these example, several
unit and platform tracks have
duplicate names. Unless you are
constantly monitoring the track
lists in the TrackPlot Injector,
then you would not easily detect
the discrepancies. Similarly, you
would have to view the
properties of each track to detect
duplicate UIC and or URN entries.
These C2PC MOE features aid in
ensuring the track reporting is

- _jj Duplicate Tracks
+ | Trackname

i Cl UIC
-]-Ca URN

I + 2151111 , 1 BN 5 MAR
I 2151111 , 3 BN 5 MAR
•■■■■ 2151111 , UIBN

Ifl -P'l Active MOE Alerts

NAI/TAI - Named
Areas of Interest /
Target Area of
Interest - is a simple
utility that the S-2
can use to monitor a
NAI/TAI for hostile
track activity.

Use C2PC Overlays
(circle, rectangle or
box) for the NAI/TAI.
MOE monitors for
any HOS/SUS unit
tracks breaching or
leaving the
geometry of the
NAI/TAI.

NAI/TAI uses pop-up
dialogs and, if
desired, sound to
alert events.

Each NAI/TAI alert is
recorded in a history
log.

311MRE

lias entered Named Area of Interest:

Acknowledge

THEN

WPNS5I

lias left Named Area of Liter est:

'ill- 1 111 I-

COA1.NAI 1

Latitude

Longitude

Timed fReport

311MRB

33.43S1 37G11G

030349:502 Aug 03

NAI Alert!- 31 1MRB

NAI Alert!

NAI Alert! - UI BN

NAI Alert!

NAI/TAI

Latitude

Longitude

Bearing

Radius

Lf

C0A1.NA1 1
C0A1.NAI 3
C0A1.NAI 2

33.3786111111

33.4586111111

33.3884444444

-117.315
-1 1 7.403333332
-1 1 7.422777777

118

1.241801

4

[Add NAi/TAi]]

Clear All

□ K

-1

u..

MOE List

r4-P^ Active MOE Alerts
□-E NAI/TAI
F NAI 1
F NAI 2
F NAI 3

Er F Decision Point

□ LOD/SND
r Brevity Code

□ Key Track?
n MrssjrsgKep Tracks

□ MTO

O C2PC Network Status

^ Overlay Files & Segments

0 COAl.mgc

NA1 1

NAI 2
NAI 3

\k IOW5903P1.mgc

Bowl

Circlel
Rectanglel

Link MOE to
current C2PC
Overlay NAI
obj e cts.

DP - Decision Point -
is a simple utility that
the S-2/3 can use to
create and monitor a
DP for any friendly or
hostile unit(s) to trip.
When tripped, an
alert with an
associated DP
"actions" file can be
displayed.

DP uses the C2PC
Overlay Tactical Point
Decision Point, but
operators can add a
radius to expand the
DP "trip" boundary.
Any type of file or
URL may be
associated with the
DP to provide actions
to take when the DP
is tripped.

Each DP trip event is
recorded in a history
log.

DP Agent

WFNS 5 MAR

]^1 Done

§:m..|

TFiK

flTTR

v 1

mu.

MOE List

SHS T rack Attribute Check

EE J Timelate FRD

+ _] Timelate HOS
iQ Missing FRD
+ _J Missing HOS

Duplicate T racks
Active MOE Alerts
$-|7 NAI/TAI
SH0 Decision Point
[7 DP A
0 DP B

□ LGD/BND
n BfewfyCode
n A'ay Tracks
IJ Missing Key Tracks

□ MTO

- n C2PC Network Status

V

Decision Point Alert! - 3BN7M

DP Alert!

3BN7MAR

has entered a Decision Point:
COA1.DP A

Acknowledoe Actions File

File Edit Format Help

[Take the following actions when DP 1 is tripped.

5 MAR will establish a blocking force vie 11SMS6668589620
Umar will engage en unit at firing points GP3 , GP14 and GP3 5
etc.

Decision Point Alert! - 31MR

DP Alert!

j DP Action File can be
any MS Windows/Office
file.

31MRR

has entered a Decision Point:
COA1.DP B

Acknowledge Action File

3 S3 tSJ | ^Search jg Favorites Q Media Q) -iV @ ^ J

Bj-:l *

i^Go I Links " HI

Address © 1 C:\Common Files\Moe\H6-COA2.htm

H+6 Course of Action

, U T . . T ^ ' ' ■ .k' " J

~!A oo m i/rfl nonoi n,o£-? *i i r no

DP Action File
can be a web
page or site

LOD/Bnd Agent

LD/Bnd - Line of
Departure/Boundary
- is a MOE agent the
S-3 uses to assign
and monitor when a
specified friendly
unit(s) crosses a
specific line of
departure, phase
line or limit of
advance.

LD uses the C2PC
Overlay Tactical Line
graphics for LD,
LD/LC, LOA and PL.
As units cross a
designated control
measure that
mission is alerted
and removed from
the left panel folder.

mm

WFNSEMAR

& U..1 ff $T.

to.. %

- _il

El-
El-
S-
Eh
Ei~

e-Q

El-
0"
S-

MOE List

Q T rack Attribute Check
m Timelate FRD
Timelate HOS
:_3 Missing FRD
O Missing HOS
m Duplicate Tracks
Active MOE Alerts
0 NAI/TAI
¥ Decision Point
0 LOD/BND
□™0 LD Green
¥ TF22
[7 WPNS5MAR
□ |7 LD Purple

0 1BN5MAR
0 TF33
□-0 LOA canary

1 0 3BN7MAR

Brevity Code
Key 1/ecAs
Airs wie Key frecAs
MID

LOD/Bnd

LOD/Bnd

Start Latitude

Start Longitude

End

C0A1.LD Green
C0A1.L0A canary
C0A1.LD Purple

33.3411111111111

33.3625

33.4675

-1 17.461 111 11 11 11
-117.351388888886
-117.485833333333

33.28805

33.33333

33.41844

<1

^■1

2J

Unit

LOD/Bnd

Time Of Departure

TF33

TF22

1BN7MAR

3BN7MAR

WPNS5MAR

1BN5MAR

C0A1.LD Purple
C0A1.LD Green
C0A1.L0A canary
C0A1.L0A canary
C0A1.LD Green
C0A1.LD Purple

030246: 27Z Aug 03

1BN5MAR

C0A1.LD Purple

Ml

Apply

r

r

c

Unit Name

Add LOD/Bnd

_Jl C2PC Network Status

Overlay Files & Segments

B""" COAl.mgc

LD Green

LOA canary

LD Purple

B IOW5903P1 .mgc

-TacGraphicLinel
TacGraphicLine2
TacGraphicLine3
TacGraphicLine4

7 Enable Log

Clear All

Jn|x

LOD/Bnd

LOD Alert!

1BN7MAR

lias crossed Line Of Departure:

LOA canary

Acknowledge

Each LD alert is
recorded in a history
log.

:vity Code

Brevity Code
Agent

Brevity Codes are
imported from a file
or entered in MOE. A
unit reports the
Brevity Code
changing by his
track's "Shortname"
field to the Brevity
Code which is
automatically
"broadcast" across
entire MAGTF C2PC
Network.

C2PC MOE monitors
the active track
database for Brevity
Code reporting.

C2PC MOE pops-up
an Alert window
when a Brevity Code
is detected.

The event is also
recorded in the
Brevity Code Log

id

Brevity Code List

Unit

Brevity Code

Time Of Report

Input: f

W Enable Log

Import Brv. Code

Clear All

OK

Look in:

fall"

22 Sample Alert WAV files

ZU Sample Overlays

History

Zj Sample Units udb file

H) COAl.bvc

Desktop

1

1

My Documents

u

WT^nm

File name:

IS

Files of type: J Brevity Code (*.bv

File Edit Format Help

-=!OJ_xJ

Openasread-

yellowfish, Commencing attack on OBJ B at time roadrunner
greengoat, switched to comm plan yankee
reddog, Ready and positioned for attack on OBJ c
bluebird, obstacles breached in zone tulip
BROWNFOX, Passage of lines with TF22 completed

Ld

31

J3

• u..j

&

i

Go-

&m..|

E _J MDE List

Q3 T rack Attribute Check

+ | Timelate FRD

+ J Timelate HOS

| iQ Missing FRD

+ | Missing HOS

i ffi-Q Duplicate Tracks
S-ft Active MOE Alerts
j~F NAI/TAI
+ F Decision Point

| s-F lod/bnd

Et F Brevity Code

I j F BLUEBIRD

I I F BROWNFOX

| F GREENGOAT

I I F REDDOG

! i U0 YELLOWFISH

i r Key Tracks

j O Mrss&xj Key Tracks

i n MTO

L -iLJl C2PC Network Status

Symbology | Track Numbers ] Last Report] History] Remar * I *

Attributes

1BN7MAR

□TH REAL-WORLD LU39305

Brevity Code Alert! - 1BN7MAR

Brevity Code Alert!

Embarked:
Orig XRef:

Cancel

Name:

Short Name:
Alert:
Category:
Threat:

Flag:

Real World
/ Exercise:
UIC:

Apply

|none

3

|lnd

3

|frd

3

1

|real-wdrld

Org Type:
Echelon:
Service:
Platform:

BE Number: [
OSuffix:

URN:

1BN7MAR

lias reported Codeword:

BLUEBIRD

Acknowledge

Key Track names
entered by a
reporting unit in the
"Name" field are
"broadcasts" across
entire MAGTF C2PC
Network.

C2PC MOE monitors
all C2PC unit tracks
that are being
created or deleted.

If the tack name
matches the Key
Track or Missing Key
Track list then an
Alert is trigger -
even if not in current
map view.

Key Tracks might be
a HVT/HPT initial
detection/reporting
or the unit of main
effort.

C2PC MOE records
all Key Track alerts
in the Key Track

Key Track/Missing Key Track

Agent

wmm l

35RAG

|SHj TW ' '

Acknowledge

"4in

M

2BN5MAR

was just created in the C2PC Database

Acknowledge

Key Track Alert! -35RAG

Key Track Alert!

gJS KeyTrack Alert! - 2BN5MAR

Key Track Alert!

MOE List

_] Track Attribute Check
j &□ Timelate FRD
1 Q Timelate HOS
\ B 03 Missing FRD
!■■■■■♦ 5MAR
♦ 1MARDIV
Izl-tt Missing HOS
!■■■■■♦ 312MRB
25RAG

i'Q Duplicate Tracks
13 -Q Active MOE Alerts
i S' F NAI/TAI
I Eh0 Decision Point
j g-F LOD/BND
il y Brevity Code
B y Key Tracks
I | j 0 25RAG

! ! ! 0 2BN5MAR

| | L F 31 2MRB

- y Missing Key Tracks
j ! I 0 1LARBN

j 0 31MRR

| 0 35RAG

I ! l F TF33
* r MW

1 Cj C2PC Network Status

MTO Agent

l|^#f|®C?0

B-t3;

vlOE List

TRK

flTTR

Mfil np UJU EfiUT £ 7 ,, r*@ 1_P

TAI ur .v IS CODE ^ B w

Q Track Attribute Chec
Fjn-I I Timelate FFlD
Fjn-I I Timelate HOS
- -03 Missing FRD

MTO Alert! - 8/3/2003 3:15:55 A

^MTO

*1

MTO Alert!

1 + 5MA.Fi

1

|l11726:05ZNov 03

|l 11726:052 Nov 03

^ + 1MARDIV

l j:. i inr-

TF22

Start of Movement

Time to Objective

+ 312MRB
+ 25RAG

m-r~l Duplicate Tracks
- -0| Active MOE Alerts

lias started its mission

| eO 0

NAI/TAI

i $ 0

Decision Point

i ai 3

LOD/BND

I ai 3

Brevity Code

j a 0

Key T racks

rti-.r7

Missinn Kpu T r^nks

a -0

MTO

a-

w OBJ A

1 0 TF22

Acknowledge

ur

Add Obj

Unit Name

Objective

Update Freq (Minutes)

Status

Unit

Objective

Last Position Report

Pending

TF22

C0A2. Alpha

■ I ■ ■

<1 i v i i u aaa mission Torm *\

0 Enable Log

II C2FC Network Status

MTO - Movement to Objective - is simple routine that the
OPS O can use to monitor a MTO mission from start of
movement to the objective (C2PC Objective Overlay).

gg MTO Alert! - 8/3/2003 3:20:56 AM GMT

JfiJxj

MTO Alert!

MTO uses a simple "as the crow flies” algorithm to
determine if the unit will make it to the objective at the
specified time based on his rate of movement. MTO will
also alert if the unit has not moved or moved further away
in the specified reporting period.

TF22

lias reached the mission objective

Acknowledge

If unit cannot make it to the objective on time the
Commander may have to change his entire battle plan.

The Alert Logs, if enabled,
record each event being alerted
based on your MOE criteria. It
can be a simple After Action
Report of the critical events for
the operation.

Each active overlay (DP, NAI,
Brevity Code, Key Track, Missing
Key Track, MTO, and LOD) has
it's own log which can be
enabled independently.

There is also an aggregate log.

The log is maintained in the
MOE database and can be
printed or saved as a
"delimited" file so you can
import into Excel and conduct
refined analysis.

Alerts will be recorded, if
enabled on the individual tabs,
even when the alert pop-ups are
deactivated.

Alert Logs (~AAR)

Ik J **** \ 1

I ■ • SL _ ‘ ■■ ■ ■ . V

~ T™ "t * * ‘i i.

wl [U

4‘l» '*r i> ! £ -:V

W 1 JfeWi fe-» f.i

-mj

The Network Status
Agent is a simple
ping utility that the
Watch Officer/Chief
uses to monitor the
C2PC reporting units.

Use the “Network
Status" form to
import or enter the
unit name and IP
address of each
C2PC in your CTP
reporting
architecture.

Set the Network
query interval for
auto ping.

The units are added
to the network status
folder in the C2PC
panel to continuously
monitor the status of

11SMS5 190397262

=]©C%>|

- _J MOE List

Q Track Attribute Check
+ _] Timelate FRD
Itl-Pl Timelate HOS
S-fi Missing FRD
+ 5MAR

♦ 1MARDIV
Fr-fj§ Missing HOS

♦ 312MRB

♦ 25RAG

B-O Duplicate Tracks
a-® Active MOE Alerts
a- PI NAI/TAI
Ek-p] D ecision Point
i-p LOD/BND
+ y Brevity Code
EEl-p Key Tracks
a- p M issing Key T racks

i r MT8

f’1 C2PC Network Status

TRK ftj NM n P ILM BRUT rb,.

flTTR ~ Tfll .v WM CODE ^

Network Status Agent

Gl'I^t]

Q

Status | Unit

Look in: | td Moe

Zll Sample Alert WAV files
Zl Sample Overlays
Zl Sample Units udb file
^1 COA1 Network, ipa

Desktop

Network Query Period (minutes)

P

My Documents

Input: I

File name:
Files of type:

C0A1 Network.ipa

| IP Address files ( K .ipa)
V~ Open as read-only

Import Unit/IP

Clear All

COA1 Network.ipa - Notepad

File Edit Format Help

[LMAR, 123.4.5.6
5 MAR, 192.168.0.23
2BN5MAR, 127.0.0.2
7MAR, 200.145.0.34
UMAR, 192.168.0.102
1MARDIV, 192.168.0.101
I MEF, 127. 0. 0.1

+ y Missing Key Tracks

| i □ MW

- C2PC Network Status

i ^ ii mar

I ^ 1MAR

| i 1 MAFIDIV

| ^ 2BN5MAFI

I ^ 5MAR

| i 7MAR
i 'T I MEF

^Network Status

Status

Unit

1MAR

5MAR

2BN5MAR

7MAR

11 MAR

1MARDIV

I MEF

123.4.5.G

192.168.0. 23

127.0. 0.2

200.145.0. 34

192.168.0. 102

192.168.0. 101

127.0. 0.1

Network Query Period (minutes)

P

Limit

Import Unit/IP Clear All OK

your reporting units

Planned for v2.1

Upgrade to 6.0 APIs

Combat Effectiveness attribute check

Modify Key Track monitoring (create, delete,
move)

Modify Phase line alerts
Timelate by attributes
NAI alerts by attributes
Branching DP alerts

Hostile unit Danger Close range alerts for specific
units

Submit your v2.2 requirements now!

Call or E-mail:

CB Brown at 1-800-299-8474 or email cb.brown@titan.com
Stephen Barber at 1-888-278-1830 or email stephen.barber@titan.com